Using DNS2Go with Web Servers

Last updated: January 2026

Overview

DNS2Go makes it easy to host and access a web server on a home or office Internet connection, even when your public IP address changes. By automatically updating your DNS records, DNS2Go ensures your website or web application remains reachable at all times.

How DNS2Go Works with Web Servers

Internet connections with dynamic IP addresses can change without notice. DNS2Go continuously monitors your public IP and updates your domain so visitors can always reach your web server using a consistent hostname.

Common Use Cases

• Hosting personal or small business websites
• Self-hosted dashboards or internal tools
• Development and staging environments
• Home lab and testing projects
• Temporary or private web services

Basic Requirements

• An active DNS2Go account and domain
• The DNS2Go Client running on your network
• A web server application (IIS, Apache, Nginx, etc.)
• Router or firewall access for inbound connections

Web Server Configuration

Your web server should be configured to listen on the appropriate ports and respond to requests for your DNS2Go domain name.

• HTTP: TCP port 80
• HTTPS: TCP port 443
• Custom ports if required by your application

Router and Firewall Setup

Forward the required ports from your router to the internal IP address of the system hosting the web server.

• Port 80 for HTTP traffic
• Port 443 for HTTPS traffic
• Ensure firewall rules allow inbound connections

Using HTTPS

For security and browser compatibility, HTTPS is strongly recommended. Most modern certificate authorities support DNS-based or hostname-based validation.

• Use a trusted SSL/TLS certificate
• Ensure your DNS2Go domain matches the certificate
• Automatically renew certificates when possible

Testing Your Web Server

1. Confirm the DNS2Go Client shows your domain as online
2. Open a browser and navigate to your DNS2Go hostname
3. Test from outside your local network
4. Verify pages load correctly over HTTP or HTTPS

Troubleshooting Tips

• Confirm your domain resolves to the correct public IP
• Verify port forwarding and firewall rules
• Ensure your web server service is running
• Check server logs for connection or binding errors
• Confirm your ISP is not blocking inbound ports

Security Considerations

Hosting a web server on a public connection exposes it to the Internet. Follow best practices to reduce risk.

• Keep your web server software up to date
• Limit access to administrative interfaces
• Use strong authentication where applicable
• Monitor logs for unusual activity

Need Help?

If you need assistance setting up DNS2Go with your web server, contact the Deerfield Support team and we’ll be happy to get you taken care of.

← Back to Knowledge Base